Welcome to Cryostat! 👋

Before contributing, make sure you have:

• Read the contributing guidelines
• Linked a relevant issue which this PR resolves
• Linked any other relevant issues, PR's, or documentation, if any
• Resolved all conflicts, if any
• Rebased your branch PR on top of the latest upstream main branch
• Attached at least one of the following labels to the PR: [chore, ci, docs, feat, fix, test]
• Signed all commits using a GPG signature

To recreate commits with GPG signature git fetch upstream && git rebase --force --gpg-sign upstream/main

See cryostatio/cryostat-helm#184

Description of the change:

Switches out the HTTP client library used by the S3 (storage) client from JDK urlconnection to Apache HTTP.

Motivation for the change:

https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/http-configuration.html

Apache HTTP should be more performant and robust than urlconnection, and supports the full S3 API feature set.

After splitting out the storage container to a separate Deployment with a separate Service I observe some connection flakiness and instability, where Cryostat API requests dealing with storage (archive actions, querying custom event templates) often respond with sporadic HTTP 500 responses. Retrying identical requests tends to work, so I wonder if switching out the backing HTTP client will help stabilize this.

How to manually test:

1. Build PR, or use quay.io/andrewazores/cryostat:s3-apache-1
2. With a Kubernetes or OpenShift cluster, deploy the image from this PR with split deployments a la feat(deployment): split out -db and -storage deployments cryostat-helm#184 : helm install cryostat --set authentication.openshift.enabled=true --set core.route.enabled=true --set core.image.repository=quay.io/andrewazores/cryostat --set core.image.tag=s3-apache-1 --set pvc.enabled=true ./charts/cryostat/
3. Go to Event Templates view, upload a custom event template.
4. Create a new recording (on Cryostat or another target) using the custom event template
5. Wait some time, then repeatedly archive the recording
6. Try to generate reports on archived recordings
7. Delete archived recordings
8. Delete the custom event template
9. The above actions should all complete with a high degree of reliability, ie. few (ideally 0) HTTP 5xx exceptions